-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: clarify napi_finalize related APIs #29797
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
doc
Issues and PRs related to the documentations.
node-api
Issues and PRs related to the Node-API.
labels
Oct 1, 2019
legendecas
changed the title
n-api,doc: clarify napi_finalize related APIs
doc: clarify napi_finalize related APIs
Oct 1, 2019
gabrielschulhof
approved these changes
Oct 1, 2019
All these APIs have napi_finalize parameter but they don't behave exactly the same. Fixes: nodejs#29750
legendecas
force-pushed
the
issue-29750
branch
from
October 2, 2019 01:13
ab41da1
to
7543a4a
Compare
This comment has been minimized.
This comment has been minimized.
trivikr
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Oct 2, 2019
Trott
approved these changes
Oct 3, 2019
mhdawson
approved these changes
Oct 3, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Landed in a71fb97 |
Trott
pushed a commit
that referenced
this pull request
Oct 3, 2019
All these APIs have napi_finalize parameter but they don't behave exactly the same. Fixes: #29750 PR-URL: #29797 Reviewed-By: Gabriel Schulhof <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
BridgeAR
pushed a commit
that referenced
this pull request
Oct 9, 2019
All these APIs have napi_finalize parameter but they don't behave exactly the same. Fixes: #29750 PR-URL: #29797 Reviewed-By: Gabriel Schulhof <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
doc
Issues and PRs related to the documentations.
node-api
Issues and PRs related to the Node-API.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All these APIs have napi_finalize parameter but they don't behave
exactly the same.
Fixes: #29750
Checklist